home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Plus Extra 1997 #4
/
Amiga Plus Extra 1997 #4.iso
/
pd
/
netz
/
voyager10
/
v.readme
< prev
next >
Wrap
Text File
|
1997-06-09
|
5KB
|
112 lines
Voyager 1.0 Release Notes
=========================
Voyager 1.0 is a freely distributable WWW browser for AmigaOS.
Its range of features covers:
o It's faaaast. On the average, Voyager outruns any other available Amiga
Web browser by a factor of two.
o Supports the full HTML-2 standard as described in RFC-1866, including forms.
It doesn't want to be a reference implementation, though, and tries to make
the best even out of malformed documents.
o Supports many proposed so called HTML-3 extensions.
o Supports Client Side Image Maps.
o Supports Netscape-Level 1 (NHTML) extensions, including <center>, floating
images, background images and text coloring (both RGB and named colors).
o Supports HTTP access authorization.
o Supports ftp, gopher and wais via proxy.
o Supports news: usenet news reading and posting.
o Supports interfacing to mail readers and telnet clients for mailto:
and telnet: URLs.
o Document cache with optional automatic last-modified-date-based verify.
o Versatile hierarchical bookmark system, allowing export in HTML format,
menu selection and drag'n'drop sorting.
o Full support for true color displays with V43 datatypes.
o Asynchronous network handling. Multiple windows.
o works with Miami, AmiTCP, as225r2, inet225 and mlink.
o can be used without a network package as a local file viewer
(esspecially useful with client-side-image-maps)
Voyager 1.0 is released now as a free gift to the Amiga community. Our
main development efforts are currently gearing towards the release of
Voyager 2.0 (our internal name is "V - Next Generation"), which is
currently in alpha stage. You can find more information about V-NG on
http://www.vapor.com/support/voyager/ng.html
Copyright and License
---------------------
Voyager 1.0 is Copyright © 1996 by Oliver Wagner (owagner@lsd.wupper.de),
All Rights Reserved.
Voyager 1.0 is provided free of charge. It may be copied freely via ftp or
web sites as long as the whole archive remains intact and no part is
modified in any way. Distribution via other means requires prior
permission (which might normally be granted free of charge for "freeware
compilation" disks or CDs).
Voyager 1.0 is provided "as-is"; no warranties, either implied or expressed,
are made regarding the viability of the program. The entire risk of the
use of Voyager is carried by the user. If you don't agree to this license,
you must not use it and delete all associated files immediately.
Installation
------------
Please use the provided installer script for correct installation. You
also need MUI 3.3 (preferably the release version; cracked version are
known to cause trouble) and GIF and JPEG datatypes. Voyager is known to
work well with the V43 datatypes available on AmiNet; you might want to
install them if you are running obscure datatypes and are experiencing
crashes on page swaps.
Voyager documentation is included in HTML format, it will be automatically
loaded when you first start the program.
Bugs
----
Although Voyager has undergone thorough testing, it's very likely that bugs
will remain. If you find a bug, please report it to owagner@lsd.wupper.de.
Don't forget to add a description on how to recreate the bug and a close
description of your system. Please don't send enhancement requests
or reports of misinterpreted or missing html stuff, because the html
engine won't be changed in favour for the Voyager 2.0 release.
Known problems
--------------
If you experience a straight crash when starting V, you're having a problem
with your cache directory, most likely because you installed an old pirated
alpha version before. V alpha versions before 0.81 sometimes did
SetComment() with more than 80 chars, triggering a very nasty bug in the
FFS which disrupts partition data. Install V in a different directory and
try to get rid of the old cache directory.
If your system deadlocks during running V, you're most likely running an
very old menu/cycletomenu hack commoditiy or a application using boopsi
gadgetclass gadgets. This is not a V bug, but a non-handled deadlock
situation in the other application. The same effect can be triggered with
every other application that updates scroller gadgets under program control
like V does (all GUI IRC clients, for example). The solution is to put the
buggy application to a different screen so the risk of a LockLayer()
Intuition deadlock is reduced. Note that this problem has been constantly
reported by people who had run V and AWeb on the same screen for
comparision purposes. Don't install a ObtainGIRPort()-Hack of any kind,
otherwise you may risk your overall system stability.